The following documentation contains test scripts
and expected results for validating the CDISC Builder
tool. Do the following to verify proper
installation:
-
Perform each test by performing the steps specified
by the instructions.
- Evaluate the results of each step by comparing
them with results described in the Documentation
column.
Instructions 1
The following instructions are accomplished
through Windows Explorer.
-
Navigate to the validation sub-directory named
"saspgm".
-
Right mouse click on the "fmtsum1.sas" program
and select Batch Submit.
-
Review the fmtsum1.log and verify that the following
messages are produced.
-
ERROR: [fmtsum] is missing a required parameter
FMTPATH.
-
ERROR: [fmtsum] found in invalid data specification:
invalid
-
ERROR: [fmtsum] had in invalid
path to the specified BACKCODE.
Instructions 2
The following instructions are accomplished
through Windows Explorer.
-
Navigate to the validation sub-directory named
"saspgm".
-
Right mouse click on the "fmtsum2.sas" program
and select Batch Submit.
-
Verify that all the formats in the formats catalogs
are reported in the fmtsum2.lst. You can
compare this to the same file in the benchmark
area.
Instructions 3
The following instructions are accomplished
through Windows Explorer.
-
Navigate to the validation sub-directory named
"saspgm".
-
Right mouse click on the "fmtsum3.sas" program
and select Batch Submit.
-
Verify that all the formated and informated
variables are captured and reported in fmtsum3.lst.
You can verify this against the fmtsum3.lst
in the benchmark folder.
Instructions 4
The following instructions are accomplished
through Windows Explorer.
-
Navigate to the validation sub-directory named
"saspgm".
-
Right mouse click on the "fmtsum4.sas" program
and select Batch Submit.
-
Verify that no errors were created in fmtsum4.log.
-
Verify that program fmtsum4_back.sas was created.
-
Right mouse click on fmtsum4_back.sas and select
"Batch Submit" to run the test.
- Verify the log of
fmtsum4_back.log, fmtsum4.log and fmtsum4.lst
against the corresponding file in the benchmark
area.
For more information, please contact MXI
.
|